\chapter{State Dynamics Viewpoint}
\label{cap:StateDynamicsViewpoint}

\section{User State Dynamics}

Here we present the state diagram which try to explain the user's specific expressed before in the requirement analysis document.
Within this diagram we find the states, that represent the qualification of a determined user in a certain instant of time, and the transactions, which are tags with the operation or event name which is necessary in order to attempt/wait for in order to make the user change his own qualification in the system and so change the actions that he's allowed to attempt.
This diagram is important to be sure to implement the system with respect to the user without violating the project specific.
We can underline mainly two things: a founder can't delete it's own account without nominating a new founder, likewise a banned user can't delete his own account before the end of the ban.

\begin{figure}[htbp]
	\centering
	\includegraphics[scale = 0.4]{images/user_state.pdf}
	\caption{User dynamics UML State Diagram\label{fig:userstate}}
\end{figure}